feat: disable per-tracker/MPPT entities by default - #445
Merged
tomer-w merged 1 commit intoJun 26, 2026
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follows up on tomer-w/victron_mqtt#103 (Q1).
Multi-tracker chargers (e.g. SmartSolar MPPT RS 450/200 with 4 PV trackers) produce ~8 per-tracker entities each, all updating on every keepalive cycle. On installations with several such chargers this easily adds up to dozens of continuously-recorded entities that most users never look at — device-level totals cover the common case.
What this PR does:
Adds 14 per-tracker / per-MPPT
generic_short_ids to the existingENTITIES_DISABLE_BY_DEFAULTlist inentity.py:tracker_{n}_power/voltage/current/operation_mode/name/max_power_today/max_voltage_today/yield_todaymppt_{n}_yield_today/yield_yesterday/state/power/voltage/currentSafe for existing installations:
entity_registry_enabled_defaultonly affects entities that don't yet exist in the registry. Any entity already registered keeps its current enabled/disabled state — no history, no automations, nounique_ids are affected.Users who want the per-tracker breakdown can enable the entities individually in HA (Settings → Entities → show disabled).